Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8692c0b934b85cf24bdf31a84463fae24ad3a647fd4ee1a16c37ee66f8b427dc

Tx prefix hash: b22fe764e6394012e617bdb7897ad9baf47f51f3cfbef858748b67fe7c114134
Tx public key: 484f4f0e7a04f3cb727aaf38ee40ea3b54555de7a680b7e43bf9b1b34ae8d6e9
Timestamp: 1634744458 Timestamp [UCT]: 2021-10-20 15:40:58 Age [y:d:h:m:s]: 04:014:18:02:43
Block: 356886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1047095 RingCT/type: yes/0
Extra: 01484f4f0e7a04f3cb727aaf38ee40ea3b54555de7a680b7e43bf9b1b34ae8d6e902110000000936fe6557000000000000000000

1 output(s) for total of 40.317068364000 dcy

stealth address amount amount idx
00: 2a0b73223be1997894dfbc4d36a85263b5f63c33689578146991717b347ad5b6 40.317068364000 727962 of 0

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": 356896, "vin": [ { "gen": { "height": 356886 } } ], "vout": [ { "amount": 40317068364, "target": { "key": "2a0b73223be1997894dfbc4d36a85263b5f63c33689578146991717b347ad5b6" } } ], "extra": [ 1, 72, 79, 79, 14, 122, 4, 243, 203, 114, 122, 175, 56, 238, 64, 234, 59, 84, 85, 93, 231, 166, 128, 183, 228, 59, 249, 177, 179, 74, 232, 214, 233, 2, 17, 0, 0, 0, 9, 54, 254, 101, 87, 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