Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab9d53ebb9f073cfcf42c35cba506118fb2270f4b214a2507f10d742ede1aa70

Tx prefix hash: bc8650928754522ea8dc28660e4689fe3a58900c5706a00aebce2d2e371d57df
Tx public key: 9c0dca838e0b057236b8103110d5686804d902039a4c1590ab9b8cc98af6a7b0
Timestamp: 1734125773 Timestamp [UCT]: 2024-12-13 21:36:13 Age [y:d:h:m:s]: 00:322:00:45:11
Block: 1174569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227650 RingCT/type: yes/0
Extra: 019c0dca838e0b057236b8103110d5686804d902039a4c1590ab9b8cc98af6a7b00211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2c7907f4d6519c8acf4dc3e6665612390a70a73e3458fd3bddbb139c1c87286 0.600000000000 1660736 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": 1174579, "vin": [ { "gen": { "height": 1174569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2c7907f4d6519c8acf4dc3e6665612390a70a73e3458fd3bddbb139c1c87286" } } ], "extra": [ 1, 156, 13, 202, 131, 142, 11, 5, 114, 54, 184, 16, 49, 16, 213, 104, 104, 4, 217, 2, 3, 154, 76, 21, 144, 171, 155, 140, 201, 138, 246, 167, 176, 2, 17, 0, 0, 0, 7, 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