Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c69df43abe932891c166c452de76f1b9748f8cc258cc58b4c799cce598008ea

Tx prefix hash: 81ff317f7c3d870e5c18ac9e9fdafde6cfd6a85a9dbb515546173e4b505cc8be
Tx public key: e2b595c94a42c5ffcc8038070692e02c7498cf587131d397a264379f25daa42a
Timestamp: 1713628999 Timestamp [UTC]: 2024-04-20 16:03:19 Age [y:d:h:m:s]: 02:214:10:32:18
Block: 1004719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 678386 RingCT/type: yes/0
Extra: 01e2b595c94a42c5ffcc8038070692e02c7498cf587131d397a264379f25daa42a0211000000060011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c2a9a7a2225c3cab236613cf3a224d09d869c76860776007b87a6b7ccf84d259 0.000600000000 1465291 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": 1004729, "vin": [ { "gen": { "height": 1004719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2a9a7a2225c3cab236613cf3a224d09d869c76860776007b87a6b7ccf84d259" } } ], "extra": [ 1, 226, 181, 149, 201, 74, 66, 197, 255, 204, 128, 56, 7, 6, 146, 224, 44, 116, 152, 207, 88, 113, 49, 211, 151, 162, 100, 55, 159, 37, 218, 164, 42, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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: