Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3a64627bc05b6c966f72f9fcc8d20b02c82b5806ca7e2f31a8b06ebf79e77d5

Tx prefix hash: 86d63a0931076ae7f65fae01b9e157b1358a9134ab8e5439981c7de70d653b75
Tx public key: 0f89094c208ee343e6a04fb66d6d0385f9a89a087f31a4277d97e00e5eb17e4c
Timestamp: 1774948645 Timestamp [UTC]: 2026-03-31 09:17:25 Age [y:d:h:m:s]: 00:229:11:47:58
Block: 1509698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169464 RingCT/type: yes/0
Extra: 010f89094c208ee343e6a04fb66d6d0385f9a89a087f31a4277d97e00e5eb17e4c021100000009e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 452ee0c053b36a2b5b19aad0d3682feaeebe78fa79fbbdbca1f38cd2a1deefbf 0.000600000000 1999474 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": 1509708, "vin": [ { "gen": { "height": 1509698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "452ee0c053b36a2b5b19aad0d3682feaeebe78fa79fbbdbca1f38cd2a1deefbf" } } ], "extra": [ 1, 15, 137, 9, 76, 32, 142, 227, 67, 230, 160, 79, 182, 109, 109, 3, 133, 249, 168, 154, 8, 127, 49, 164, 39, 125, 151, 224, 14, 94, 177, 126, 76, 2, 17, 0, 0, 0, 9, 227, 215, 220, 159, 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: