Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60cddf1d2f8da8415497b935f24f98d8240d99043357e763a05fa140296d154d

Tx prefix hash: d130292676a500a0bfbd8752647fdcfb5f21965a7102d69cec0f7adc7f09f583
Tx public key: 41ea961566fdea4596f878ed19284df68cfe7dd6b3646c33b1fffb7f8ac8f75f
Timestamp: 1743516381 Timestamp [UCT]: 2025-04-01 14:06:21 Age [y:d:h:m:s]: 00:037:04:00:33
Block: 1252019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26580 RingCT/type: yes/0
Extra: 0141ea961566fdea4596f878ed19284df68cfe7dd6b3646c33b1fffb7f8ac8f75f0211000000064060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31daa8c8ca4997a79d5b7851a1b58bb9e3412d043f51eae9ce5571009d348052 0.600000000000 1739096 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": 1252029, "vin": [ { "gen": { "height": 1252019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31daa8c8ca4997a79d5b7851a1b58bb9e3412d043f51eae9ce5571009d348052" } } ], "extra": [ 1, 65, 234, 150, 21, 102, 253, 234, 69, 150, 248, 120, 237, 25, 40, 77, 246, 140, 254, 125, 214, 179, 100, 108, 51, 177, 255, 251, 127, 138, 200, 247, 95, 2, 17, 0, 0, 0, 6, 64, 96, 246, 210, 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