Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 457edc08d95ab86d608a85112b014a60633d5040cf80295efbcab7413adcaabf

Tx prefix hash: c88c7f553fde29193a7908c68e3376432ef4d54dacb7f7f59685da6a2d0697c0
Tx public key: d0145c5c9a2ec1610c38f74d261c91cdd60969e13a948c9371e1514da8c00302
Timestamp: 1730647799 Timestamp [UCT]: 2024-11-03 15:29:59 Age [y:d:h:m:s]: 00:172:23:02:09
Block: 1145754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123457 RingCT/type: yes/0
Extra: 01d0145c5c9a2ec1610c38f74d261c91cdd60969e13a948c9371e1514da8c0030202110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e9fdeb7a46c89e9986fcda9732f59a2c99ad4775eeb219083cc5d00c51d292e 0.600000000000 1630253 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": 1145764, "vin": [ { "gen": { "height": 1145754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e9fdeb7a46c89e9986fcda9732f59a2c99ad4775eeb219083cc5d00c51d292e" } } ], "extra": [ 1, 208, 20, 92, 92, 154, 46, 193, 97, 12, 56, 247, 77, 38, 28, 145, 205, 214, 9, 105, 225, 58, 148, 140, 147, 113, 225, 81, 77, 168, 192, 3, 2, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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