Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cec05d71f1655198dba863cec448f8dd39dc29dadd13aa73e0b20275db08437

Tx prefix hash: 1cbd4e919ad8caf1b805f391045b415fa087c7c7f379c518b21b22e123bd80fc
Tx public key: 856aec2209752a79d4eb8648f8b6a341028618efd3f62f4b130b3a5a0146eaee
Timestamp: 1736077001 Timestamp [UCT]: 2025-01-05 11:36:41 Age [y:d:h:m:s]: 00:350:08:55:40
Block: 1190721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247949 RingCT/type: yes/0
Extra: 01856aec2209752a79d4eb8648f8b6a341028618efd3f62f4b130b3a5a0146eaee0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb6d1430c1d8695c4d152a2c25a2ec0598fdca8efc41b0faaca25b3df047127c 0.600000000000 1677240 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": 1190731, "vin": [ { "gen": { "height": 1190721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb6d1430c1d8695c4d152a2c25a2ec0598fdca8efc41b0faaca25b3df047127c" } } ], "extra": [ 1, 133, 106, 236, 34, 9, 117, 42, 121, 212, 235, 134, 72, 248, 182, 163, 65, 2, 134, 24, 239, 211, 246, 47, 75, 19, 11, 58, 90, 1, 70, 234, 238, 2, 17, 0, 0, 0, 3, 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