Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d5210d11ae0ab517d80cb1c262523ef5c816eb7ec3cece3126175346cb35c78

Tx prefix hash: 707a87a4694576ed4147bafa220979406abdb57b4edfee54660b29d4385ab0d2
Tx public key: bb226541c0f1e47aeda4ca06095955f49d0740da012b097e4f0aec52156935d5
Timestamp: 1741265398 Timestamp [UCT]: 2025-03-06 12:49:58 Age [y:d:h:m:s]: 00:307:19:40:13
Block: 1233401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217812 RingCT/type: yes/0
Extra: 01bb226541c0f1e47aeda4ca06095955f49d0740da012b097e4f0aec52156935d5021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f335cb46e9df55b26de623f59080197c5ee1fcca0614b4b873b8a8d41253fc5a 0.600000000000 1720322 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": 1233411, "vin": [ { "gen": { "height": 1233401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f335cb46e9df55b26de623f59080197c5ee1fcca0614b4b873b8a8d41253fc5a" } } ], "extra": [ 1, 187, 34, 101, 65, 192, 241, 228, 122, 237, 164, 202, 6, 9, 89, 85, 244, 157, 7, 64, 218, 1, 43, 9, 126, 79, 10, 236, 82, 21, 105, 53, 213, 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