Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b56d6a0e56c8bc22bed6b6a4cffa038a9d5d742d43dbeda37ed7d9c3353a47a7

Tx prefix hash: 53f8163136371a7b933b5138f5e11dfc113441f1990db2c1fb9d0c3e30dccdd1
Tx public key: b2d9eef222e9c8404afa796e13d509dad715d432d90a7e3004f425f6649745bd
Timestamp: 1624975280 Timestamp [UTC]: 2021-06-29 14:01:20 Age [y:d:h:m:s]: 04:319:09:45:25
Block: 285286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1247903 RingCT/type: yes/0
Extra: 01b2d9eef222e9c8404afa796e13d509dad715d432d90a7e3004f425f6649745bd021100000020b8178fc1000000000000000000

1 output(s) for total of 0.069619286154 xmr

stealth address amount amount idx tag
00: 7b8625374229e4dde703fc13ea4892b1d37899afa4870d6abaf021374ac504a0 0.069619286154 597305 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": 285296, "vin": [ { "gen": { "height": 285286 } } ], "vout": [ { "amount": 69619286154, "target": { "key": "7b8625374229e4dde703fc13ea4892b1d37899afa4870d6abaf021374ac504a0" } } ], "extra": [ 1, 178, 217, 238, 242, 34, 233, 200, 64, 74, 250, 121, 110, 19, 213, 9, 218, 215, 21, 212, 50, 217, 10, 126, 48, 4, 244, 37, 246, 100, 151, 69, 189, 2, 17, 0, 0, 0, 32, 184, 23, 143, 193, 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: