Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64410da9c15e74b08ef7460c404581277407aaea4534af1d01c8d40d76b6da8d

Tx prefix hash: 599ffc91676caf426a425b8d1dec6db511f5eefcfd40e8bb9ad11a3d0c832b48
Tx public key: 670acd66d3738232811b5489255def479a421a7a35822a2c0163837479ecd4b5
Timestamp: 1574714045 Timestamp [UCT]: 2019-11-25 20:34:05 Age [y:d:h:m:s]: 05:001:01:57:24
Block: 17401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1143585 RingCT/type: yes/0
Extra: 01670acd66d3738232811b5489255def479a421a7a35822a2c0163837479ecd4b5021100000001f95225a5000000000000000000

1 output(s) for total of 537.457520386000 dcy

stealth address amount amount idx
00: edf1a884a88397b201cd9e33351aa63e3a17781a03a4406c8a954b1c0a011fe3 537.457520386000 25241 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": 17411, "vin": [ { "gen": { "height": 17401 } } ], "vout": [ { "amount": 537457520386, "target": { "key": "edf1a884a88397b201cd9e33351aa63e3a17781a03a4406c8a954b1c0a011fe3" } } ], "extra": [ 1, 103, 10, 205, 102, 211, 115, 130, 50, 129, 27, 84, 137, 37, 93, 239, 71, 154, 66, 26, 122, 53, 130, 42, 44, 1, 99, 131, 116, 121, 236, 212, 181, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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