Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afa49640d78d82582782c26b7e65953598c61e924da176f7ee5929e7c0eb871e

Tx prefix hash: 8a26b5778b47e03824947b9120799f68d28a15ea0f978030b3cefb914b044483
Tx public key: 1f9447761a09bcccce5f2ac4cb8a3af23321dddbae6d8e276b95d7e4e4cc65b0
Timestamp: 1727385011 Timestamp [UCT]: 2024-09-26 21:10:11 Age [y:d:h:m:s]: 01:042:14:59:38
Block: 1118776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288858 RingCT/type: yes/0
Extra: 011f9447761a09bcccce5f2ac4cb8a3af23321dddbae6d8e276b95d7e4e4cc65b0021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41a998c81ba4348f6efdf7f7e980cfa612d15c43f199a58419014792de45106d 0.600000000000 1600089 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": 1118786, "vin": [ { "gen": { "height": 1118776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41a998c81ba4348f6efdf7f7e980cfa612d15c43f199a58419014792de45106d" } } ], "extra": [ 1, 31, 148, 71, 118, 26, 9, 188, 204, 206, 95, 42, 196, 203, 138, 58, 242, 51, 33, 221, 219, 174, 109, 142, 39, 107, 149, 215, 228, 228, 204, 101, 176, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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