Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 923f0db523847f2c57a1ad652e77ebbbf29e429789871bbc26c3d26379ea0baa

Tx prefix hash: d88b314a69084681fb3aa74a3ec5cc9c53646727d81ecb815192574720c998bf
Tx public key: b8cebb3aa1ee80e6e20e123f8025f4ce35cec3c384ecfb17e90c03ea00af35b7
Timestamp: 1702061183 Timestamp [UCT]: 2023-12-08 18:46:23 Age [y:d:h:m:s]: 01:345:23:04:06
Block: 908825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506147 RingCT/type: yes/0
Extra: 01b8cebb3aa1ee80e6e20e123f8025f4ce35cec3c384ecfb17e90c03ea00af35b702110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 788cc0f7086a6963f9c5f727f4798863429c8fb877cc5f73f58f84a0cc51be0c 0.600000000000 1365882 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": 908835, "vin": [ { "gen": { "height": 908825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "788cc0f7086a6963f9c5f727f4798863429c8fb877cc5f73f58f84a0cc51be0c" } } ], "extra": [ 1, 184, 206, 187, 58, 161, 238, 128, 230, 226, 14, 18, 63, 128, 37, 244, 206, 53, 206, 195, 195, 132, 236, 251, 23, 233, 12, 3, 234, 0, 175, 53, 183, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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