Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48e13088335fda8ac6907bcd66d60e0aeb509a4865e66fd1f9ac1a55357512f4

Tx prefix hash: fbef342d93f36fce0cc7f73f27ba5e9675a5f8a05bf7a87fba832f415ec6f586
Tx public key: 3f3b475518e315e763ae8602a27007dcfabd3c87cf825ab72dc84a0527c83607
Timestamp: 1762864167 Timestamp [UCT]: 2025-11-11 12:29:27 Age [y:d:h:m:s]: 00:042:13:26:39
Block: 1409798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30464 RingCT/type: yes/0
Extra: 013f3b475518e315e763ae8602a27007dcfabd3c87cf825ab72dc84a0527c83607021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5efae7ccabd4dd460e070e9ce55058a9d278d1e3c32574f21b45ab86f2a7a156 0.600000000000 1898245 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": 1409808, "vin": [ { "gen": { "height": 1409798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5efae7ccabd4dd460e070e9ce55058a9d278d1e3c32574f21b45ab86f2a7a156" } } ], "extra": [ 1, 63, 59, 71, 85, 24, 227, 21, 231, 99, 174, 134, 2, 162, 112, 7, 220, 250, 189, 60, 135, 207, 130, 90, 183, 45, 200, 74, 5, 39, 200, 54, 7, 2, 17, 0, 0, 0, 1, 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