Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38624d3635a0bff65627a385cbf39d3994feefd8e14c95638ce37ad5ea861b45

Tx prefix hash: 67f2ecc738838407be382a9970ec2f61aeeb11c2bf8e18708fb1d8112e872f4d
Tx public key: eb37be5eb1a87b8ae86f5252815394ad83ed82a53fedcaea9c4747b5fb58a92e
Timestamp: 1736468567 Timestamp [UCT]: 2025-01-10 00:22:47 Age [y:d:h:m:s]: 00:155:04:42:47
Block: 1193952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110661 RingCT/type: yes/0
Extra: 01eb37be5eb1a87b8ae86f5252815394ad83ed82a53fedcaea9c4747b5fb58a92e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80cd73c4ab90fa9dadb4c18ae867714991f930d664e9da63e574d337e8a610a2 0.600000000000 1680517 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": 1193962, "vin": [ { "gen": { "height": 1193952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80cd73c4ab90fa9dadb4c18ae867714991f930d664e9da63e574d337e8a610a2" } } ], "extra": [ 1, 235, 55, 190, 94, 177, 168, 123, 138, 232, 111, 82, 82, 129, 83, 148, 173, 131, 237, 130, 165, 63, 237, 202, 234, 156, 71, 71, 181, 251, 88, 169, 46, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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