Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18811d7d9b4211ff62401dc652e8176f8dd3cb3e06bae1d56ef679ff4b813d4f

Tx prefix hash: a24ee5b0da06bab2dce2674317f2b3cf0ad3b3e9f5becccdda743e4a480441ea
Tx public key: d4fe8f5a2c4a5247fb767b49eaef10e730eb8d3ee0db2099f883505fbbdc8abf
Timestamp: 1719163929 Timestamp [UCT]: 2024-06-23 17:32:09 Age [y:d:h:m:s]: 00:363:22:46:52
Block: 1050607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259940 RingCT/type: yes/0
Extra: 01d4fe8f5a2c4a5247fb767b49eaef10e730eb8d3ee0db2099f883505fbbdc8abf0211000000070fbbc4c5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 209ddc95c8874e8573af55a66ecb1b23c310229cb931f0d173386b11875352a8 0.600000000000 1520782 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": 1050617, "vin": [ { "gen": { "height": 1050607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "209ddc95c8874e8573af55a66ecb1b23c310229cb931f0d173386b11875352a8" } } ], "extra": [ 1, 212, 254, 143, 90, 44, 74, 82, 71, 251, 118, 123, 73, 234, 239, 16, 231, 48, 235, 141, 62, 224, 219, 32, 153, 248, 131, 80, 95, 187, 220, 138, 191, 2, 17, 0, 0, 0, 7, 15, 187, 196, 197, 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