Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74145ab9936a317062c9cb84a98482774c4e71bdb3afec7fc7d675f428e32a44

Tx prefix hash: f771512b257e315ca803235464929ef51be576a92cda3ae91f30c86c9b3273ac
Tx public key: e7bb102cba7d5e6ccfc193e8b107e85bfe778e7930d55ebcd6caf3b479f950cb
Timestamp: 1714209677 Timestamp [UCT]: 2024-04-27 09:21:17 Age [y:d:h:m:s]: 00:308:09:55:05
Block: 1009545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220454 RingCT/type: yes/0
Extra: 01e7bb102cba7d5e6ccfc193e8b107e85bfe778e7930d55ebcd6caf3b479f950cb0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8e934b41a431623791e9f00542b602f0f4f4748ce7c50e4df3e84df7576d233 0.600000000000 1471249 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": 1009555, "vin": [ { "gen": { "height": 1009545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8e934b41a431623791e9f00542b602f0f4f4748ce7c50e4df3e84df7576d233" } } ], "extra": [ 1, 231, 187, 16, 44, 186, 125, 94, 108, 207, 193, 147, 232, 177, 7, 232, 91, 254, 119, 142, 121, 48, 213, 94, 188, 214, 202, 243, 180, 121, 249, 80, 203, 2, 17, 0, 0, 0, 4, 0, 17, 5, 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