Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e59529ae7dfa8e0434299c1f72dc9d223e8ab30445436941bb505c666cb4c70

Tx prefix hash: 27513a77e31a1f2e15dcab4402088a342879396c5feaf096e750df64fef8d1a8
Tx public key: ae52b5d2ddf65265e97de653cfb7e99f3651596e4120870e3e53aa077e64df4a
Timestamp: 1724209433 Timestamp [UCT]: 2024-08-21 03:03:53 Age [y:d:h:m:s]: 00:153:20:49:49
Block: 1092457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110018 RingCT/type: yes/0
Extra: 01ae52b5d2ddf65265e97de653cfb7e99f3651596e4120870e3e53aa077e64df4a02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91be335e1780f57449f53c2ea046085fd35f40eb446cfc96e7c7c33ebce42338 0.600000000000 1567208 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": 1092467, "vin": [ { "gen": { "height": 1092457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91be335e1780f57449f53c2ea046085fd35f40eb446cfc96e7c7c33ebce42338" } } ], "extra": [ 1, 174, 82, 181, 210, 221, 246, 82, 101, 233, 125, 230, 83, 207, 183, 233, 159, 54, 81, 89, 110, 65, 32, 135, 14, 62, 83, 170, 7, 126, 100, 223, 74, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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