Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b03fd0065de2771e3b6ac531f83bd920376b105fe3aba8c59a619440e94ea1f8

Tx prefix hash: a5908f8388fa3ab8b102e7f3354b6cd9005d1308280b2c2bf407dcc3499ca6b7
Tx public key: a95683c7cb2e804d2ac7426c9f6fab581224c759abba0778c023c04feddcd355
Timestamp: 1749709917 Timestamp [UCT]: 2025-06-12 06:31:57 Age [y:d:h:m:s]: 00:155:18:05:16
Block: 1303281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109026 RingCT/type: yes/0
Extra: 01a95683c7cb2e804d2ac7426c9f6fab581224c759abba0778c023c04feddcd355021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc7f9044d1bff69657dcd7d05bdd73622e4197ddb9f1ef373656d2f2bb499687 0.600000000000 1790860 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": 1303291, "vin": [ { "gen": { "height": 1303281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc7f9044d1bff69657dcd7d05bdd73622e4197ddb9f1ef373656d2f2bb499687" } } ], "extra": [ 1, 169, 86, 131, 199, 203, 46, 128, 77, 42, 199, 66, 108, 159, 111, 171, 88, 18, 36, 199, 89, 171, 186, 7, 120, 192, 35, 192, 79, 237, 220, 211, 85, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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