Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff974aec91ad4cbb3f24e85001af73a3c53b37338b627bc777561a2f744c547f

Tx prefix hash: 2f09831916afe4ff9fd627ec39d7aa31d0a4ac487953fe5157a3a224c76842a8
Tx public key: 6df339b3fc4601ac1a9372cefdcd2d8fa81ec0e0783d8105eee8497af9cf3de2
Timestamp: 1741277989 Timestamp [UCT]: 2025-03-06 16:19:49 Age [y:d:h:m:s]: 00:006:01:33:14
Block: 1233499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4352 RingCT/type: yes/0
Extra: 016df339b3fc4601ac1a9372cefdcd2d8fa81ec0e0783d8105eee8497af9cf3de2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ef692ca0c76096b25fb9bda599f6d28e7bc60513b7ab7a3328f2d418a90ecb8 0.600000000000 1720420 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": 1233509, "vin": [ { "gen": { "height": 1233499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ef692ca0c76096b25fb9bda599f6d28e7bc60513b7ab7a3328f2d418a90ecb8" } } ], "extra": [ 1, 109, 243, 57, 179, 252, 70, 1, 172, 26, 147, 114, 206, 253, 205, 45, 143, 168, 30, 192, 224, 120, 61, 129, 5, 238, 232, 73, 122, 249, 207, 61, 226, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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