Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6e3d28714a00a1c59f5fe4017e13839fb33302c14439111d5dc62d80b3a1216

Tx prefix hash: 3b8d8c270871c6a7625a87c324cf0441ec76e7c4ffbb9c08ffd7a870cb6fedbb
Tx public key: cfb0e4f5305a7840fa9ee71269131421fdb6f8eae40f77b4daa262f0ced68189
Timestamp: 1772983672 Timestamp [UTC]: 2026-03-08 15:27:52 Age [y:d:h:m:s]: 00:259:00:01:30
Block: 1493451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190043 RingCT/type: yes/0
Extra: 01cfb0e4f5305a7840fa9ee71269131421fdb6f8eae40f77b4daa262f0ced68189021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: de66a346ee71b2345cd4d4ae8481da49d65f70f12b040aab60719a0046fb7921 0.000600000000 1983011 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": 1493461, "vin": [ { "gen": { "height": 1493451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de66a346ee71b2345cd4d4ae8481da49d65f70f12b040aab60719a0046fb7921" } } ], "extra": [ 1, 207, 176, 228, 245, 48, 90, 120, 64, 250, 158, 231, 18, 105, 19, 20, 33, 253, 182, 248, 234, 228, 15, 119, 180, 218, 162, 98, 240, 206, 214, 129, 137, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: