Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee6f6cd09219be98005b78aff17e2642ac53e227c7efbbb0ff84834beccacab0

Tx prefix hash: f1df6e1897ccf3315bb0d0d580dcf3e37df69cf339ba0e90be782d7e1933d9c4
Tx public key: 5a2777b0ab325ee8cfef6f5ce64b67ce05bb041c256f8b38dd60eb5a54fb81fa
Timestamp: 1641910863 Timestamp [UTC]: 2022-01-11 14:21:03 Age [y:d:h:m:s]: 04:306:16:01:15
Block: 415009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1262197 RingCT/type: yes/0
Extra: 015a2777b0ab325ee8cfef6f5ce64b67ce05bb041c256f8b38dd60eb5a54fb81fa021100000013edb0d4a3000000000000000000

1 output(s) for total of 0.025876362946 xmr

stealth address amount amount idx tag
00: bf7ebef937fb53f5b4137de8fc5ae71bbe4aa79fc52f1e5fd1640629f71830b2 0.025876362946 820607 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": 415019, "vin": [ { "gen": { "height": 415009 } } ], "vout": [ { "amount": 25876362946, "target": { "key": "bf7ebef937fb53f5b4137de8fc5ae71bbe4aa79fc52f1e5fd1640629f71830b2" } } ], "extra": [ 1, 90, 39, 119, 176, 171, 50, 94, 232, 207, 239, 111, 92, 230, 75, 103, 206, 5, 187, 4, 28, 37, 111, 139, 56, 221, 96, 235, 90, 84, 251, 129, 250, 2, 17, 0, 0, 0, 19, 237, 176, 212, 163, 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: