Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf1dc87d10a9984e39b5bbeefb944fcc329fc31cabbfbdb6a8241b57468363c4

Tx prefix hash: 574d908458afa0ad7f49ab354803cb27780740377b3c3d44ae261ae28ed3ddd2
Tx public key: fa15447030554396fd934df563b2cc54ad0dc7b15ed33c15af599a7d89d3084c
Timestamp: 1751594563 Timestamp [UCT]: 2025-07-04 02:02:43 Age [y:d:h:m:s]: 00:129:02:09:30
Block: 1318319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90515 RingCT/type: yes/0
Extra: 01fa15447030554396fd934df563b2cc54ad0dc7b15ed33c15af599a7d89d3084c02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db3d42bc19d09e00147e445ed578af49e8af0c1b78d6472801f024a386c7fa0f 0.600000000000 1805998 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": 1318329, "vin": [ { "gen": { "height": 1318319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db3d42bc19d09e00147e445ed578af49e8af0c1b78d6472801f024a386c7fa0f" } } ], "extra": [ 1, 250, 21, 68, 112, 48, 85, 67, 150, 253, 147, 77, 245, 99, 178, 204, 84, 173, 13, 199, 177, 94, 211, 60, 21, 175, 89, 154, 125, 137, 211, 8, 76, 2, 17, 0, 0, 0, 3, 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