Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4134a81ae9564063a4ca1c0e3eeb1dfd54bbda8aedea949464321295dba3706a

Tx prefix hash: f5d9e52ed9dbb70fd4b2783d8f19d2f56f9a239d1c6bb457dc39e5369b0ad8c9
Tx public key: 1988fcb1a4ce73137881a192a14020c370a1d022f83819ebc000315dc35ae837
Timestamp: 1702924487 Timestamp [UCT]: 2023-12-18 18:34:47 Age [y:d:h:m:s]: 01:069:02:55:38
Block: 915990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310496 RingCT/type: yes/0
Extra: 011988fcb1a4ce73137881a192a14020c370a1d022f83819ebc000315dc35ae83702110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6161dcd8989736d70dc371f013dae6632d1b0ee8afc551fda2f7f91c575be93b 0.600000000000 1373424 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": 916000, "vin": [ { "gen": { "height": 915990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6161dcd8989736d70dc371f013dae6632d1b0ee8afc551fda2f7f91c575be93b" } } ], "extra": [ 1, 25, 136, 252, 177, 164, 206, 115, 19, 120, 129, 161, 146, 161, 64, 32, 195, 112, 161, 208, 34, 248, 56, 25, 235, 192, 0, 49, 93, 195, 90, 232, 55, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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