Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dbd0533c3e7dff71d6e701a5a41ea7a80ba684709fdbe83a8cbd984fbdd2883

Tx prefix hash: a1c00817e94d331001d58498bd812a67d0e00d3fab26825eccc94b706088e1b5
Tx public key: 3de8f6fb01c1c7361ea988f66d4a4779c62db22fb3fb9f0710729e3360e2b21e
Timestamp: 1756397990 Timestamp [UTC]: 2025-08-28 16:19:50 Age [y:d:h:m:s]: 01:084:03:07:44
Block: 1356391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326504 RingCT/type: yes/0
Extra: 013de8f6fb01c1c7361ea988f66d4a4779c62db22fb3fb9f0710729e3360e2b21e0211000000032609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e1574b7aea8bb5e377244a9fbad137a48b5ff228651c1f5c21431ac6ce185ffe 0.000600000000 1844400 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 dinastycoin-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": 1356401, "vin": [ { "gen": { "height": 1356391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1574b7aea8bb5e377244a9fbad137a48b5ff228651c1f5c21431ac6ce185ffe" } } ], "extra": [ 1, 61, 232, 246, 251, 1, 193, 199, 54, 30, 169, 136, 246, 109, 74, 71, 121, 198, 45, 178, 47, 179, 251, 159, 7, 16, 114, 158, 51, 96, 226, 178, 30, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: