Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99748317cafa0e675d2f28e31ea97a4a68dd348d169a35f7f733a747ca7a9d34

Tx prefix hash: b88bb6ce47e5e79e7113156e0508a955fc5453cfd8a087a70fc700bd98b26f1c
Tx public key: 87c15a0b20d24f19431c30376b2c8dca81173f51154245933240e8b1033d8b5c
Timestamp: 1750815157 Timestamp [UCT]: 2025-06-25 01:32:37 Age [y:d:h:m:s]: 00:219:09:02:18
Block: 1312193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154648 RingCT/type: yes/0
Extra: 0187c15a0b20d24f19431c30376b2c8dca81173f51154245933240e8b1033d8b5c021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1ff6eb6afb9726d2882dfb9aad1f25f5dfd0e46572aa1e387db42b41024afb4 0.600000000000 1799824 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": 1312203, "vin": [ { "gen": { "height": 1312193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1ff6eb6afb9726d2882dfb9aad1f25f5dfd0e46572aa1e387db42b41024afb4" } } ], "extra": [ 1, 135, 193, 90, 11, 32, 210, 79, 25, 67, 28, 48, 55, 107, 44, 141, 202, 129, 23, 63, 81, 21, 66, 69, 147, 50, 64, 232, 177, 3, 61, 139, 92, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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