Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d70751b50cf24aec2c9313708131458a2ea3870b8f080b8c9468e59563d8f7e

Tx prefix hash: 85be5a37a898b0a7c4712d4d7fa84043268474da027c19773d86d6d8e7871685
Tx public key: 1a99fb5fb1200c18554794afb7c4c512a9b85bad1b6748ad137d9f0a4032c7f6
Timestamp: 1695567373 Timestamp [UCT]: 2023-09-24 14:56:13 Age [y:d:h:m:s]: 01:061:23:30:01
Block: 855195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305552 RingCT/type: yes/0
Extra: 011a99fb5fb1200c18554794afb7c4c512a9b85bad1b6748ad137d9f0a4032c7f6021100000003faf35c9c000000000000000000

1 output(s) for total of 0.900293274000 dcy

stealth address amount amount idx
00: 2da54fde4f566c223e21b6a744bfbb99aed8dceb5463d894ff12a353e5a7aae3 0.900293274000 1309201 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": 855205, "vin": [ { "gen": { "height": 855195 } } ], "vout": [ { "amount": 900293274, "target": { "key": "2da54fde4f566c223e21b6a744bfbb99aed8dceb5463d894ff12a353e5a7aae3" } } ], "extra": [ 1, 26, 153, 251, 95, 177, 32, 12, 24, 85, 71, 148, 175, 183, 196, 197, 18, 169, 184, 91, 173, 27, 103, 72, 173, 19, 125, 159, 10, 64, 50, 199, 246, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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