Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5872ce25bb1f33bff8cc8fbd59843d4d20969121cdd9a535caf762df55f6a1cb

Tx prefix hash: 18ad1255c192d828d1d9b2c8735ec98a775b1f93dce302c10d8b301d026560d8
Tx public key: e67533ecc8723fc2a355f9d9c001bd946f4d3726c4329ae500d74adaead8b43d
Timestamp: 1718100895 Timestamp [UCT]: 2024-06-11 10:14:55 Age [y:d:h:m:s]: 00:302:17:17:09
Block: 1041823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216327 RingCT/type: yes/0
Extra: 01e67533ecc8723fc2a355f9d9c001bd946f4d3726c4329ae500d74adaead8b43d02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e693f935f370836c91aa2831f32384d11c9a248a5747763dc0f0e9138206d495 0.600000000000 1510592 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": 1041833, "vin": [ { "gen": { "height": 1041823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e693f935f370836c91aa2831f32384d11c9a248a5747763dc0f0e9138206d495" } } ], "extra": [ 1, 230, 117, 51, 236, 200, 114, 63, 194, 163, 85, 249, 217, 192, 1, 189, 148, 111, 77, 55, 38, 196, 50, 154, 229, 0, 215, 74, 218, 234, 216, 180, 61, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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