Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61259cb823ffb74eee37baf75daef5db09615c2821780c4647e6f41c5d6844c3

Tx prefix hash: 165fb6f186984ab86f7693b020cb51de089d14483d31feaa461db3f32a093078
Tx public key: 552bb146ed2ae1d5e9f36bf7787cc22741258eba8796eae86f3f262db08caa60
Timestamp: 1612803479 Timestamp [UTC]: 2021-02-08 16:57:59 Age [y:d:h:m:s]: 05:286:13:25:47
Block: 194660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1488563 RingCT/type: yes/0
Extra: 01552bb146ed2ae1d5e9f36bf7787cc22741258eba8796eae86f3f262db08caa60021100000022c6b81c9d000000000000000000

1 output(s) for total of 0.138998861631 xmr

stealth address amount amount idx tag
00: b5350351c0d613dd610f49d9f163e089b1e0a3b34a2d7d33ae2dd4454441d59d 0.138998861631 395512 of 0 -

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": 194670, "vin": [ { "gen": { "height": 194660 } } ], "vout": [ { "amount": 138998861631, "target": { "key": "b5350351c0d613dd610f49d9f163e089b1e0a3b34a2d7d33ae2dd4454441d59d" } } ], "extra": [ 1, 85, 43, 177, 70, 237, 42, 225, 213, 233, 243, 107, 247, 120, 124, 194, 39, 65, 37, 142, 186, 135, 150, 234, 232, 111, 63, 38, 45, 176, 140, 170, 96, 2, 17, 0, 0, 0, 34, 198, 184, 28, 157, 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: