Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fdc4e9e8a516fd16294725b2063c0cb3de5621e507bb0da52c39502bc44a55e

Tx prefix hash: 4473490e18ee625a38592fb64fd98f9ccace8f6ac01c8b68b988d349d7318f43
Tx public key: 771f8a2ba2778eaaf6cef00595807b3a3ce333a59194403230a9b112c92f66df
Timestamp: 1758943130 Timestamp [UCT]: 2025-09-27 03:18:50 Age [y:d:h:m:s]: 00:098:03:00:41
Block: 1377300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70276 RingCT/type: yes/0
Extra: 01771f8a2ba2778eaaf6cef00595807b3a3ce333a59194403230a9b112c92f66df021100000005a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ded1dc4b3f4ba8d2f5b77c2e1fcfe0bc714a58dd4c550713133b7674604fd63 0.600000000000 1865391 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": 1377310, "vin": [ { "gen": { "height": 1377300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ded1dc4b3f4ba8d2f5b77c2e1fcfe0bc714a58dd4c550713133b7674604fd63" } } ], "extra": [ 1, 119, 31, 138, 43, 162, 119, 142, 170, 246, 206, 240, 5, 149, 128, 123, 58, 60, 227, 51, 165, 145, 148, 64, 50, 48, 169, 177, 18, 201, 47, 102, 223, 2, 17, 0, 0, 0, 5, 165, 220, 205, 121, 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