Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a021449db24139e769fea0811650e0d103f505e36aa06a20d40dc6d182c1991

Tx prefix hash: 0f0796766db71fb2921e8c0e58d9a304668c69224c6ca5f48009e4c51e04b1d2
Tx public key: 534301142e953d5cb12ff58dd22f283794effe0f0eb95957f6943b726fb1af3d
Timestamp: 1709715353 Timestamp [UCT]: 2024-03-06 08:55:53 Age [y:d:h:m:s]: 00:353:22:35:20
Block: 972305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253034 RingCT/type: yes/0
Extra: 01534301142e953d5cb12ff58dd22f283794effe0f0eb95957f6943b726fb1af3d02110000000146812bb8000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4d0ebd1141594ee4dc2603d11492df81a8ad2735bc656e82ac69e24db38c77b 0.600000000000 1432214 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": 972315, "vin": [ { "gen": { "height": 972305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4d0ebd1141594ee4dc2603d11492df81a8ad2735bc656e82ac69e24db38c77b" } } ], "extra": [ 1, 83, 67, 1, 20, 46, 149, 61, 92, 177, 47, 245, 141, 210, 47, 40, 55, 148, 239, 254, 15, 14, 185, 89, 87, 246, 148, 59, 114, 111, 177, 175, 61, 2, 17, 0, 0, 0, 1, 70, 129, 43, 184, 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