Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f66924501ee9bf043de2498fb8f5cce0117e8b94d40682abcd5653ce15e8c57

Tx prefix hash: 6c40dbab7fa63d58435aaf2cfe0da197b1d74a540c9aae8e4a3cf1e9e091c29f
Tx public key: 7fc3469fbff5e5c0bdcfba3848f6e33e2be00504ba3397f90950c6efe3846129
Timestamp: 1722658697 Timestamp [UCT]: 2024-08-03 04:18:17 Age [y:d:h:m:s]: 00:081:16:22:47
Block: 1079603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58477 RingCT/type: yes/0
Extra: 017fc3469fbff5e5c0bdcfba3848f6e33e2be00504ba3397f90950c6efe3846129021100000004daef6b5b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae68287f84637dde6b5165537b33957d6a2775daf02bdb7d5785b233d39c1fd5 0.600000000000 1552626 of 15

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": 1079613, "vin": [ { "gen": { "height": 1079603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae68287f84637dde6b5165537b33957d6a2775daf02bdb7d5785b233d39c1fd5" } } ], "extra": [ 1, 127, 195, 70, 159, 191, 245, 229, 192, 189, 207, 186, 56, 72, 246, 227, 62, 43, 224, 5, 4, 186, 51, 151, 249, 9, 80, 198, 239, 227, 132, 97, 41, 2, 17, 0, 0, 0, 4, 218, 239, 107, 91, 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