Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa0771652ebd4d9c2866a6372927ea3beeb6b06178d9113a6269c6f3a07ea734

Tx prefix hash: 8c5c0aaf47e7e9198e7ac2dc5dab72190945d259195a1850ef17beca50d157e9
Tx public key: 53d048bb783a1365c90c5ea8d22a54c27e28e8d7553af79591063c6e8f89dfcc
Timestamp: 1749198312 Timestamp [UCT]: 2025-06-06 08:25:12 Age [y:d:h:m:s]: 00:161:00:25:18
Block: 1299073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112767 RingCT/type: yes/0
Extra: 0153d048bb783a1365c90c5ea8d22a54c27e28e8d7553af79591063c6e8f89dfcc02110000000843846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b111ac9a34159016ec7b0d628665885346f8d9c245dbc00c2a352aeca6199b55 0.600000000000 1786608 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": 1299083, "vin": [ { "gen": { "height": 1299073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b111ac9a34159016ec7b0d628665885346f8d9c245dbc00c2a352aeca6199b55" } } ], "extra": [ 1, 83, 208, 72, 187, 120, 58, 19, 101, 201, 12, 94, 168, 210, 42, 84, 194, 126, 40, 232, 215, 85, 58, 247, 149, 145, 6, 60, 110, 143, 137, 223, 204, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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