Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dda74761e6c5cc3756866e26ce25f6a713c475453b6c226ce51e155d980ed9e8

Tx prefix hash: f96e6bcf4b088b8834cba5cdb5c62cfa090f0727f62c4ee7eaad6e2868f36b9a
Tx public key: 6235e9b8bba789af580ec35dbcf520c5e7852d4ddcd21b93b14a1be0b9de202e
Timestamp: 1713601591 Timestamp [UCT]: 2024-04-20 08:26:31 Age [y:d:h:m:s]: 00:285:09:43:33
Block: 1004493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204028 RingCT/type: yes/0
Extra: 016235e9b8bba789af580ec35dbcf520c5e7852d4ddcd21b93b14a1be0b9de202e02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea2b73b3c17536c839a4f621a7ded30d8d0eeaa57cfae4220eb3abf1e8799253 0.600000000000 1465061 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": 1004503, "vin": [ { "gen": { "height": 1004493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea2b73b3c17536c839a4f621a7ded30d8d0eeaa57cfae4220eb3abf1e8799253" } } ], "extra": [ 1, 98, 53, 233, 184, 187, 167, 137, 175, 88, 14, 195, 93, 188, 245, 32, 197, 231, 133, 45, 77, 220, 210, 27, 147, 177, 74, 27, 224, 185, 222, 32, 46, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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