Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 515bf593aad79f91ff67531e18d29a2b6f06d4d7c0e7f0e21fbd915b4dafe998

Tx prefix hash: 9f2399fab993e9a6b3f8f2113476a556dd7430ab0ee5d0fde89c307e198518e8
Tx public key: bc917d43defcbd0669f1fe30b004e5e6b5af9a763dac9dca3945e3f8a81c5afe
Timestamp: 1582318515 Timestamp [UCT]: 2020-02-21 20:55:15 Age [y:d:h:m:s]: 05:079:15:06:32
Block: 69707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1210152 RingCT/type: yes/0
Extra: 01bc917d43defcbd0669f1fe30b004e5e6b5af9a763dac9dca3945e3f8a81c5afe021100000002c71d3ff9000000000000000000

1 output(s) for total of 360.605690980000 dcy

stealth address amount amount idx
00: 94f62b85f906ec164a6941ad6733fce62ff3cc6bee8e49239bae255c2afad47a 360.605690980000 128632 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 69717, "vin": [ { "gen": { "height": 69707 } } ], "vout": [ { "amount": 360605690980, "target": { "key": "94f62b85f906ec164a6941ad6733fce62ff3cc6bee8e49239bae255c2afad47a" } } ], "extra": [ 1, 188, 145, 125, 67, 222, 252, 189, 6, 105, 241, 254, 48, 176, 4, 229, 230, 181, 175, 154, 118, 61, 172, 157, 202, 57, 69, 227, 248, 168, 28, 90, 254, 2, 17, 0, 0, 0, 2, 199, 29, 63, 249, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8