Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 557755300d26541f367b60ff187b515aa5d65396de88039e2b0929bd473e15df

Tx prefix hash: 27f4c7fb35ee5d0c741906a24d10573e1722b81165d24e9b8f3ebd09cb51de81
Tx public key: 94c83a988063e84745843ba7292f61d10856257d8b78b21d4573bbe4f8587a28
Timestamp: 1758566973 Timestamp [UTC]: 2025-09-22 18:49:33 Age [y:d:h:m:s]: 01:057:14:43:06
Block: 1374189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307602 RingCT/type: yes/0
Extra: 0194c83a988063e84745843ba7292f61d10856257d8b78b21d4573bbe4f8587a28021100000004b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8b0ad5a99de3147c167cf78b92fcf6669afa9d1a5f553e710290bfcb5d996d26 0.000600000000 1862274 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": 1374199, "vin": [ { "gen": { "height": 1374189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b0ad5a99de3147c167cf78b92fcf6669afa9d1a5f553e710290bfcb5d996d26" } } ], "extra": [ 1, 148, 200, 58, 152, 128, 99, 232, 71, 69, 132, 59, 167, 41, 47, 97, 209, 8, 86, 37, 125, 139, 120, 178, 29, 69, 115, 187, 228, 248, 88, 122, 40, 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: