Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95cb6fdc54fbb08f5c2f94b72c107971e9047cc642b8faa46119cf9c5a0b8f1f

Tx prefix hash: 665cea21b77273c60e60250e45de27661a485adef40cdc56a1e5261aeb15bf4e
Tx public key: 0ace1c54f693550c6067e5fdc832d6fc2acf0af8c976c8f531b38ec0fdf6a3c4
Timestamp: 1696819705 Timestamp [UCT]: 2023-10-09 02:48:25 Age [y:d:h:m:s]: 01:179:11:04:13
Block: 865589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389291 RingCT/type: yes/0
Extra: 010ace1c54f693550c6067e5fdc832d6fc2acf0af8c976c8f531b38ec0fdf6a3c402110000000775e3f0e9000000000000000000

1 output(s) for total of 0.831657204000 dcy

stealth address amount amount idx
00: 5c504b65ff7ea157bb33da4ad0fe4672ba0e374fcfa29958cf0b9cf7d6dd73c4 0.831657204000 1320127 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": 865599, "vin": [ { "gen": { "height": 865589 } } ], "vout": [ { "amount": 831657204, "target": { "key": "5c504b65ff7ea157bb33da4ad0fe4672ba0e374fcfa29958cf0b9cf7d6dd73c4" } } ], "extra": [ 1, 10, 206, 28, 84, 246, 147, 85, 12, 96, 103, 229, 253, 200, 50, 214, 252, 42, 207, 10, 248, 201, 118, 200, 245, 49, 179, 142, 192, 253, 246, 163, 196, 2, 17, 0, 0, 0, 7, 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