Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e3424c914fc070813d0051b46676cc56ff913f0e7c59734df333f9613ba0a5e

Tx prefix hash: a5e8ea62bc4949c380855a5b033d00ea00cd2f98ae679b66c3b98829ee9a5dc9
Tx public key: ca3bd7e5de460e0e9be83d19b5c869acfe74cf04772a410706439b9d69d37db2
Timestamp: 1730462129 Timestamp [UCT]: 2024-11-01 11:55:29 Age [y:d:h:m:s]: 00:083:10:34:30
Block: 1144212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59648 RingCT/type: yes/0
Extra: 01ca3bd7e5de460e0e9be83d19b5c869acfe74cf04772a410706439b9d69d37db20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b84cda356c33ea8fcb62b08cb791e4e738dbb62d034e6c19a2a005b88b127ce9 0.600000000000 1628347 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": 1144222, "vin": [ { "gen": { "height": 1144212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b84cda356c33ea8fcb62b08cb791e4e738dbb62d034e6c19a2a005b88b127ce9" } } ], "extra": [ 1, 202, 59, 215, 229, 222, 70, 14, 14, 155, 232, 61, 25, 181, 200, 105, 172, 254, 116, 207, 4, 119, 42, 65, 7, 6, 67, 155, 157, 105, 211, 125, 178, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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