Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b1370b6d94df223d0df001a7a8ee547937b3152f6256bcacbdebbe37bbae62f

Tx prefix hash: 54d20a376c754ae70b03b3b8439c4386f28da59df756a5046495a5e551b00245
Tx public key: 1d09704faee3e1f10495a56bf1b8a950779c7c6bda76a534846710f2c7ae02c1
Timestamp: 1771767998 Timestamp [UTC]: 2026-02-22 13:46:38 Age [y:d:h:m:s]: 00:269:15:54:04
Block: 1483383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198289 RingCT/type: yes/0
Extra: 011d09704faee3e1f10495a56bf1b8a950779c7c6bda76a534846710f2c7ae02c1021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fdf6c70c129597c1aa8ffed78e39b246b254850af0b3d27fea7ed280ef5a08bf 0.000600000000 1972791 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": 1483393, "vin": [ { "gen": { "height": 1483383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdf6c70c129597c1aa8ffed78e39b246b254850af0b3d27fea7ed280ef5a08bf" } } ], "extra": [ 1, 29, 9, 112, 79, 174, 227, 225, 241, 4, 149, 165, 107, 241, 184, 169, 80, 119, 156, 124, 107, 218, 118, 165, 52, 132, 103, 16, 242, 199, 174, 2, 193, 2, 17, 0, 0, 0, 6, 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: