Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb250b2c19e26f102b770d90839c5362827514c308d6cd7594b8ad11ccc7e975

Tx prefix hash: a1d087d282034809ec9bead9835397e82654e4ae33357f96fc0b3ae3fd47554a
Tx public key: 8bef357c27d81e9acdf2fb8618f8f4cfcbcf570d201e64a322426545ea1b54d3
Timestamp: 1749600808 Timestamp [UTC]: 2025-06-11 00:13:28 Age [y:d:h:m:s]: 01:161:20:42:55
Block: 1302403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379748 RingCT/type: yes/0
Extra: 018bef357c27d81e9acdf2fb8618f8f4cfcbcf570d201e64a322426545ea1b54d302110000000143846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b3e20b42c538a47b5bf9e475a16bd2a64ed5656ca35bf54acc75ce69fdeb98d5 0.000600000000 1789974 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": 1302413, "vin": [ { "gen": { "height": 1302403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3e20b42c538a47b5bf9e475a16bd2a64ed5656ca35bf54acc75ce69fdeb98d5" } } ], "extra": [ 1, 139, 239, 53, 124, 39, 216, 30, 154, 205, 242, 251, 134, 24, 248, 244, 207, 203, 207, 87, 13, 32, 30, 100, 163, 34, 66, 101, 69, 234, 27, 84, 211, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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: