Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9b289b8b02cdfb2a4a6a5eac8ca9aee2f74050b9513b170cb2d45d585185811

Tx prefix hash: e6473537627beeccb26c79b294f0fcdb4d2669ddc9933a7cb7e9965ea6f83f23
Tx public key: a7f40de64ce0e23c4969ea5a106da1f43c8bd32833ac2b10b8640b5da99451ae
Timestamp: 1757945958 Timestamp [UTC]: 2025-09-15 14:19:18 Age [y:d:h:m:s]: 00:237:14:48:31
Block: 1369041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162488 RingCT/type: yes/0
Extra: 01a7f40de64ce0e23c4969ea5a106da1f43c8bd32833ac2b10b8640b5da99451ae021100000004b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9d9c4c7cb35a133a844b6fc9d6986905266d2ed2a940159081c63d0b3e317c60 0.000600000000 1857114 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": 1369051, "vin": [ { "gen": { "height": 1369041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d9c4c7cb35a133a844b6fc9d6986905266d2ed2a940159081c63d0b3e317c60" } } ], "extra": [ 1, 167, 244, 13, 230, 76, 224, 226, 60, 73, 105, 234, 90, 16, 109, 161, 244, 60, 139, 211, 40, 51, 172, 43, 16, 184, 100, 11, 93, 169, 148, 81, 174, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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: