Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3c3a6f14fc952d584fab5c4c4dac563b750cabad5935cb7a3f933abf6344642

Tx prefix hash: f16f3d1fd15665b4cdc0376beed7a732faec7be531fbe8b969fed9e37d979b4c
Tx public key: 908c9aeebc2b96a593dcab82e5360f3dda50e386e7ee4b7dcd89eceb1e64d46e
Timestamp: 1734183201 Timestamp [UCT]: 2024-12-14 13:33:21 Age [y:d:h:m:s]: 00:107:08:56:35
Block: 1175049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76510 RingCT/type: yes/0
Extra: 01908c9aeebc2b96a593dcab82e5360f3dda50e386e7ee4b7dcd89eceb1e64d46e021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fddba28d6e038ad993aa3a1f94fac0e9ac02816d99c675ede98e9071f5a7f1d0 0.600000000000 1661278 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": 1175059, "vin": [ { "gen": { "height": 1175049 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fddba28d6e038ad993aa3a1f94fac0e9ac02816d99c675ede98e9071f5a7f1d0" } } ], "extra": [ 1, 144, 140, 154, 238, 188, 43, 150, 165, 147, 220, 171, 130, 229, 54, 15, 61, 218, 80, 227, 134, 231, 238, 75, 125, 205, 137, 236, 235, 30, 100, 212, 110, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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