Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b071f3d193d747c3afba1f6445a85ead346be4fe0979bac69a506720a8744f9c

Tx prefix hash: f351176a3cef8442f3eda993288866e8a6e3cfb8c9229d7cc489a7a09d36f526
Tx public key: 8494a7be5cbe9f3adc03a28c9e39b877848e77c607912a4b6da24932571a7b87
Timestamp: 1739674429 Timestamp [UCT]: 2025-02-16 02:53:49 Age [y:d:h:m:s]: 00:350:10:53:55
Block: 1220192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248177 RingCT/type: yes/0
Extra: 018494a7be5cbe9f3adc03a28c9e39b877848e77c607912a4b6da24932571a7b87021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe0785b812534dbfe5830e78fb5186b1602a95d55bef34181cc93fcba78f85a8 0.600000000000 1707029 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": 1220202, "vin": [ { "gen": { "height": 1220192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe0785b812534dbfe5830e78fb5186b1602a95d55bef34181cc93fcba78f85a8" } } ], "extra": [ 1, 132, 148, 167, 190, 92, 190, 159, 58, 220, 3, 162, 140, 158, 57, 184, 119, 132, 142, 119, 198, 7, 145, 42, 75, 109, 162, 73, 50, 87, 26, 123, 135, 2, 17, 0, 0, 0, 3, 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