Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df1be0bd62cbe3a76b091546ac56e47b095d9123cfb9fc7a8af76d3cbda87028

Tx prefix hash: 9e563e506359125d2d0c1783fd070975453ead8e8c4d814fcd486043d163fa99
Tx public key: 94cdf41f4a3dc332eb3677a16a9a46d4834eefdd1a5de1698e21bcc7c2f17760
Timestamp: 1760939005 Timestamp [UCT]: 2025-10-20 05:43:25 Age [y:d:h:m:s]: 00:064:09:51:33
Block: 1393862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46088 RingCT/type: yes/0
Extra: 0194cdf41f4a3dc332eb3677a16a9a46d4834eefdd1a5de1698e21bcc7c2f1776002110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78f35801dae72aef32710915a2ca7113c2db05151abf85f9b016348c1f2fdcd5 0.600000000000 1882129 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": 1393872, "vin": [ { "gen": { "height": 1393862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78f35801dae72aef32710915a2ca7113c2db05151abf85f9b016348c1f2fdcd5" } } ], "extra": [ 1, 148, 205, 244, 31, 74, 61, 195, 50, 235, 54, 119, 161, 106, 154, 70, 212, 131, 78, 239, 221, 26, 93, 225, 105, 142, 33, 188, 199, 194, 241, 119, 96, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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