Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9cbc6691c95e1e582d820ab1c43b95f64aabc7f5bafa3a5cdb06d41736f810a

Tx prefix hash: f224463bf2fb442e0f9fad3d692db3bf322f7418ee0542efb48ee668b349aed8
Tx public key: ee29aec144882705f13bd73d53a2769d01f80d8f30dc4835af7718cdd9ad9c97
Timestamp: 1741993769 Timestamp [UTC]: 2025-03-14 23:09:29 Age [y:d:h:m:s]: 01:252:14:00:02
Block: 1239436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444058 RingCT/type: yes/0
Extra: 01ee29aec144882705f13bd73d53a2769d01f80d8f30dc4835af7718cdd9ad9c9702110000000b007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 970b6c42bb4a1d9691c3ac48de377ece35fe805a5cd6971476252d096499d311 0.000600000000 1726401 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": 1239446, "vin": [ { "gen": { "height": 1239436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "970b6c42bb4a1d9691c3ac48de377ece35fe805a5cd6971476252d096499d311" } } ], "extra": [ 1, 238, 41, 174, 193, 68, 136, 39, 5, 241, 59, 215, 61, 83, 162, 118, 157, 1, 248, 13, 143, 48, 220, 72, 53, 175, 119, 24, 205, 217, 173, 156, 151, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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: