Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abfd449af0b250be3f6b5dadae70b61ddaa4c10ae5dc033984cc493ea7f80c96

Tx prefix hash: 2694e3d13b37751dc80526be069868114096d85e2f0aedddf1ff85e82c930946
Tx public key: d870b3ddb73d66eb7092f9395f1fffcc07a2b585743a221450e87416605d9b52
Timestamp: 1745991395 Timestamp [UCT]: 2025-04-30 05:36:35 Age [y:d:h:m:s]: 00:204:22:41:29
Block: 1272518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144179 RingCT/type: yes/0
Extra: 01d870b3ddb73d66eb7092f9395f1fffcc07a2b585743a221450e87416605d9b5202110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3dcb9a8bba758b8588c86f60e3f8eead5c6c96f07d8beb0e1c06aae2b09e09f 0.600000000000 1759793 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": 1272528, "vin": [ { "gen": { "height": 1272518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3dcb9a8bba758b8588c86f60e3f8eead5c6c96f07d8beb0e1c06aae2b09e09f" } } ], "extra": [ 1, 216, 112, 179, 221, 183, 61, 102, 235, 112, 146, 249, 57, 95, 31, 255, 204, 7, 162, 181, 133, 116, 58, 34, 20, 80, 232, 116, 22, 96, 93, 155, 82, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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