Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56bb045b55500d5ecc4eea6bdc4f73cbf03b2708df92210db6198136e2dfd867

Tx prefix hash: bc99016bfa7f0544a98a438f22fc386b8a514965f590c417ff7ad723b4349b84
Tx public key: 57c642174ba182e734d142c2cc772081d74f88a743d6ea5a4a84e2707e2d6149
Timestamp: 1771865347 Timestamp [UTC]: 2026-02-23 16:49:07 Age [y:d:h:m:s]: 00:269:01:55:58
Block: 1484189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197891 RingCT/type: yes/0
Extra: 0157c642174ba182e734d142c2cc772081d74f88a743d6ea5a4a84e2707e2d6149021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bb093f3075fe72992a4841282684a341fc26de3a13ca757235f620183c27ea8f 0.000600000000 1973607 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": 1484199, "vin": [ { "gen": { "height": 1484189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb093f3075fe72992a4841282684a341fc26de3a13ca757235f620183c27ea8f" } } ], "extra": [ 1, 87, 198, 66, 23, 75, 161, 130, 231, 52, 209, 66, 194, 204, 119, 32, 129, 215, 79, 136, 167, 67, 214, 234, 90, 74, 132, 226, 112, 126, 45, 97, 73, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: