Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bd32b9417b40f4cf579f268294fc6562589405a5d0a23d6dd92dd3200284640

Tx prefix hash: dd110c1d9a5be21e5cae201ea1891d3e14c6eb302f63d87bfb505d46fdf0357a
Tx public key: e4231c47cde439063cee55631ca22fab76e8e5dcdd7c1db395e819eb74a1a395
Timestamp: 1734727683 Timestamp [UCT]: 2024-12-20 20:48:03 Age [y:d:h:m:s]: 00:179:06:53:34
Block: 1179567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127822 RingCT/type: yes/0
Extra: 01e4231c47cde439063cee55631ca22fab76e8e5dcdd7c1db395e819eb74a1a3950211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600110000000 dcy

stealth address amount amount idx
00: 163faeda40d584b34c298b3723e1b8d810e92a5d90c233090158bd5b7251b88f 0.600110000000 1665962 of 0

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": 1179577, "vin": [ { "gen": { "height": 1179567 } } ], "vout": [ { "amount": 600110000, "target": { "key": "163faeda40d584b34c298b3723e1b8d810e92a5d90c233090158bd5b7251b88f" } } ], "extra": [ 1, 228, 35, 28, 71, 205, 228, 57, 6, 60, 238, 85, 99, 28, 162, 47, 171, 118, 232, 229, 220, 221, 124, 29, 179, 149, 232, 25, 235, 116, 161, 163, 149, 2, 17, 0, 0, 0, 9, 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