Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4f70704e85a01913f0f6823c98c2d9bf0095147f4c6e0405e28684b15da0f8f

Tx prefix hash: 5d30b2a14095868a04e23ab21af42c08dfd6c9f3a9f99047b8af5d260456dc31
Tx public key: 612315f4876a7e815447f091c27155b411d6cc918ecf96e36a2f3dc1ab892144
Timestamp: 1761168972 Timestamp [UCT]: 2025-10-22 21:36:12 Age [y:d:h:m:s]: 00:017:03:20:44
Block: 1395758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12257 RingCT/type: yes/0
Extra: 01612315f4876a7e815447f091c27155b411d6cc918ecf96e36a2f3dc1ab892144021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a51d2345b2584549b2e20e91330f7913fe81cdd4d3e29680db70fda70ac18a1d 0.600000000000 1884041 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": 1395768, "vin": [ { "gen": { "height": 1395758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a51d2345b2584549b2e20e91330f7913fe81cdd4d3e29680db70fda70ac18a1d" } } ], "extra": [ 1, 97, 35, 21, 244, 135, 106, 126, 129, 84, 71, 240, 145, 194, 113, 85, 180, 17, 214, 204, 145, 142, 207, 150, 227, 106, 47, 61, 193, 171, 137, 33, 68, 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