Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af45e9984e7db9af05c0c2da24df8ede5d8c0ef8457962c54c6991149612ba7b

Tx prefix hash: 5514ae78b9657909902a380c36c992e9d6ebe071f6d2495d077be7d23f74a75e
Tx public key: 2c316ab6cf221d8be0f8fa01dce6d52b800aabbbbc10cf25488ab1d30938094e
Timestamp: 1732292236 Timestamp [UCT]: 2024-11-22 16:17:16 Age [y:d:h:m:s]: 00:001:15:49:34
Block: 1159372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1183 RingCT/type: yes/0
Extra: 012c316ab6cf221d8be0f8fa01dce6d52b800aabbbbc10cf25488ab1d30938094e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bce705671c7c6f94a0e968dfd2dbe070dd630d294568fd1e6e387d59801087f 0.600000000000 1645005 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": 1159382, "vin": [ { "gen": { "height": 1159372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bce705671c7c6f94a0e968dfd2dbe070dd630d294568fd1e6e387d59801087f" } } ], "extra": [ 1, 44, 49, 106, 182, 207, 34, 29, 139, 224, 248, 250, 1, 220, 230, 213, 43, 128, 10, 171, 187, 188, 16, 207, 37, 72, 138, 177, 211, 9, 56, 9, 78, 2, 17, 0, 0, 0, 2, 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