Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7547e6a922d0640c2c55cd2a9e18957231f9d64a6f28c48b0aa9b900b6b62bbc

Tx prefix hash: b6ab7ed7933e01990d3110b5a9074d81c0b4b79fde9b0eed5554ddef0b4f09ee
Tx public key: d1f60e58a360b6bf7939f0c9df576301ca04438fedce36e8667c60638218a0b9
Timestamp: 1722424048 Timestamp [UTC]: 2024-07-31 11:07:28 Age [y:d:h:m:s]: 02:111:13:09:19
Block: 1077646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 604612 RingCT/type: yes/0
Extra: 01d1f60e58a360b6bf7939f0c9df576301ca04438fedce36e8667c60638218a0b902110000000591e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 00fd4e14d7e550a6ea1f2fef797af3400ff3d1b8191ecdd89f54d807e670e77d 0.000600000000 1550201 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": 1077656, "vin": [ { "gen": { "height": 1077646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00fd4e14d7e550a6ea1f2fef797af3400ff3d1b8191ecdd89f54d807e670e77d" } } ], "extra": [ 1, 209, 246, 14, 88, 163, 96, 182, 191, 121, 57, 240, 201, 223, 87, 99, 1, 202, 4, 67, 143, 237, 206, 54, 232, 102, 124, 96, 99, 130, 24, 160, 185, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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: