Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c01bfb47fdd378ef786f8f0ff8567b0bb1efbeb1cd855afcc96e1ce51c05bef2

Tx prefix hash: 321c0164136b5609c2b50177101e820c65d9c903929f887761afba48dc120377
Tx public key: 638e8a7fdf1603eb43baf7b39eb75aa93fd5237587c99e45a6fede43533a574e
Timestamp: 1771067067 Timestamp [UTC]: 2026-02-14 11:04:27 Age [y:d:h:m:s]: 00:126:17:14:58
Block: 1477576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86813 RingCT/type: yes/0
Extra: 01638e8a7fdf1603eb43baf7b39eb75aa93fd5237587c99e45a6fede43533a574e021100000008f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3b219e47d204e045eb4284a7d781a73b808b477f0cd93cdb171b3b8894ab1d90 0.000600000000 1966894 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": 1477586, "vin": [ { "gen": { "height": 1477576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b219e47d204e045eb4284a7d781a73b808b477f0cd93cdb171b3b8894ab1d90" } } ], "extra": [ 1, 99, 142, 138, 127, 223, 22, 3, 235, 67, 186, 247, 179, 158, 183, 90, 169, 63, 213, 35, 117, 135, 201, 158, 69, 166, 254, 222, 67, 83, 58, 87, 78, 2, 17, 0, 0, 0, 8, 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: