Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f29e7ef5cc775cca7cf2d5adfc6354169bea5dd6d97d2bd53db74e2045ce909

Tx prefix hash: 01c26f21bed0be03ee72b66188b7d27b17b6a05b1cea6f63d2ec91f53699ee9e
Tx public key: bbfe0b947f0381189fd79dcca513e11ba288887178213c47dc325fdcf9a4e4e0
Timestamp: 1716208390 Timestamp [UCT]: 2024-05-20 12:33:10 Age [y:d:h:m:s]: 00:354:01:43:05
Block: 1026122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253085 RingCT/type: yes/0
Extra: 01bbfe0b947f0381189fd79dcca513e11ba288887178213c47dc325fdcf9a4e4e002110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f5989052d648219ccf9d3da2e992d3c34c2a70b64d67dd02fe8b60d130b3ca8 0.600000000000 1493035 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": 1026132, "vin": [ { "gen": { "height": 1026122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f5989052d648219ccf9d3da2e992d3c34c2a70b64d67dd02fe8b60d130b3ca8" } } ], "extra": [ 1, 187, 254, 11, 148, 127, 3, 129, 24, 159, 215, 157, 204, 165, 19, 225, 27, 162, 136, 136, 113, 120, 33, 60, 71, 220, 50, 95, 220, 249, 164, 228, 224, 2, 17, 0, 0, 0, 6, 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