Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8db5d5531cec41d4bc1e56412edc25fd1e30bb3b6b1448255ff0bc4cfc02cee2

Tx prefix hash: cbb0416378c11191165e34dea7a4cf30f2940af64ef9ca7fdc038a794249f6f8
Tx public key: 525427f7575f129e8a3f1df03c7f79b695640e60ad48237968c4e646e7532a2b
Timestamp: 1731109486 Timestamp [UCT]: 2024-11-08 23:44:46 Age [y:d:h:m:s]: 00:129:13:45:44
Block: 1149581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92434 RingCT/type: yes/0
Extra: 01525427f7575f129e8a3f1df03c7f79b695640e60ad48237968c4e646e7532a2b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbf08ecb9d3486d8a0219d158a33a2d20e17a8ca3b6582494cf2e270598048c4 0.600000000000 1634686 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": 1149591, "vin": [ { "gen": { "height": 1149581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbf08ecb9d3486d8a0219d158a33a2d20e17a8ca3b6582494cf2e270598048c4" } } ], "extra": [ 1, 82, 84, 39, 247, 87, 95, 18, 158, 138, 63, 29, 240, 60, 127, 121, 182, 149, 100, 14, 96, 173, 72, 35, 121, 104, 196, 230, 70, 231, 83, 42, 43, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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