Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11de18eec7102d648873f90036f0b98003e7feb992c4a0739b9095df9e4857ca

Tx prefix hash: b8ef89b1c3197310cb7cb19ee7e06aa21c8e24403ef2e935480bd4bdbfbb4462
Tx public key: bd9fd34a980a979f2636e51913b015ec31cb3ead49767347f99a1b585d168067
Timestamp: 1702294606 Timestamp [UCT]: 2023-12-11 11:36:46 Age [y:d:h:m:s]: 01:157:17:47:42
Block: 910769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373899 RingCT/type: yes/0
Extra: 01bd9fd34a980a979f2636e51913b015ec31cb3ead49767347f99a1b585d16806702110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a3ba21b81f5bbc9efb2a3753a98838ee45b6a5ea1dd73c06a2e53be9cbc189d 0.600000000000 1367936 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": 910779, "vin": [ { "gen": { "height": 910769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a3ba21b81f5bbc9efb2a3753a98838ee45b6a5ea1dd73c06a2e53be9cbc189d" } } ], "extra": [ 1, 189, 159, 211, 74, 152, 10, 151, 159, 38, 54, 229, 25, 19, 176, 21, 236, 49, 203, 62, 173, 73, 118, 115, 71, 249, 154, 27, 88, 93, 22, 128, 103, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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