Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 742536ade437a878891cda3e2a3eceb657622b3a1e2d409d5b3db053e27bbb50

Tx prefix hash: ade3f6b5b0ca528b95827acdecf5ac7eabe6c85fc9216b85254ba01c742324f3
Tx public key: bf2b111fc64839f4d0ea697d9dece5bbcb3e6dad183fc84b39f3cc736612c3ee
Timestamp: 1764997814 Timestamp [UCT]: 2025-12-06 05:10:14 Age [y:d:h:m:s]: 00:015:23:00:31
Block: 1427467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11434 RingCT/type: yes/0
Extra: 01bf2b111fc64839f4d0ea697d9dece5bbcb3e6dad183fc84b39f3cc736612c3ee02110000000870609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b735df0b9d4dc61285ac98dd91d386f8b2a0f3606e483c3dce9e434dbdba75ad 0.600000000000 1916168 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": 1427477, "vin": [ { "gen": { "height": 1427467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b735df0b9d4dc61285ac98dd91d386f8b2a0f3606e483c3dce9e434dbdba75ad" } } ], "extra": [ 1, 191, 43, 17, 31, 198, 72, 57, 244, 208, 234, 105, 125, 157, 236, 229, 187, 203, 62, 109, 173, 24, 63, 200, 75, 57, 243, 204, 115, 102, 18, 195, 238, 2, 17, 0, 0, 0, 8, 112, 96, 157, 3, 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