Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcaf27e90ed0c5af6273d77ea9bd7ace51a745cb74bfb20f2d4b666d57c04d17

Tx prefix hash: dffcee6e8625df019332b50f584e063e85980c078793da4753040071ae5ff224
Tx public key: cc9fedf7d913e4cb44f050970db98a584bbba6dd876ebdc8da2d888b44cbaa30
Timestamp: 1715901538 Timestamp [UCT]: 2024-05-16 23:18:58 Age [y:d:h:m:s]: 00:341:23:26:21
Block: 1023577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244432 RingCT/type: yes/0
Extra: 01cc9fedf7d913e4cb44f050970db98a584bbba6dd876ebdc8da2d888b44cbaa3002110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4da35944ce7cd3809d86fe8ff9fa6fec981d02433c6a0bdd4f4e0c16c687378f 0.600000000000 1488654 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": 1023587, "vin": [ { "gen": { "height": 1023577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4da35944ce7cd3809d86fe8ff9fa6fec981d02433c6a0bdd4f4e0c16c687378f" } } ], "extra": [ 1, 204, 159, 237, 247, 217, 19, 228, 203, 68, 240, 80, 151, 13, 185, 138, 88, 75, 187, 166, 221, 135, 110, 189, 200, 218, 45, 136, 139, 68, 203, 170, 48, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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