Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2c3e979f367ff2efc96330c3fce9e8981889a5a9bc18261980dd6b567e88a6a

Tx prefix hash: fa2258624716c0da1114bc4ced14cef25839645fc7344b94c7dac8fa83dca82a
Tx public key: 51450ef06132f6afe9ede5c848f5d0dc2f1c4348ce3f8976738d2e8d71e875d7
Timestamp: 1743731853 Timestamp [UTC]: 2025-04-04 01:57:33 Age [y:d:h:m:s]: 01:223:21:37:31
Block: 1253799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423941 RingCT/type: yes/0
Extra: 0151450ef06132f6afe9ede5c848f5d0dc2f1c4348ce3f8976738d2e8d71e875d70211000000044060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a369c5dacb1319af57a548f7a5560960a6e9243d80115abaca987ade483a0cb3 0.000600000000 1740880 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": 1253809, "vin": [ { "gen": { "height": 1253799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a369c5dacb1319af57a548f7a5560960a6e9243d80115abaca987ade483a0cb3" } } ], "extra": [ 1, 81, 69, 14, 240, 97, 50, 246, 175, 233, 237, 229, 200, 72, 245, 208, 220, 47, 28, 67, 72, 206, 63, 137, 118, 115, 141, 46, 141, 113, 232, 117, 215, 2, 17, 0, 0, 0, 4, 64, 96, 246, 210, 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: