Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c471f9d372c1ab687a693ad41e181a28de9e9be0ca3b1ca65f75d5b4f632b38

Tx prefix hash: 3130326ecfff9a686781450e759e0b5b2bdebd4c6c1c95163bc5ecec1a5706dc
Tx public key: 016148eae8dbe7eaa68d0aa57fed365271264e62eb7a48976dfce5d4922d84ad
Timestamp: 1744621248 Timestamp [UTC]: 2025-04-14 09:00:48 Age [y:d:h:m:s]: 01:029:11:52:47
Block: 1261175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271922 RingCT/type: yes/0
Extra: 01016148eae8dbe7eaa68d0aa57fed365271264e62eb7a48976dfce5d4922d84ad021100000002dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 91388c0bac6ceeadc2e14950f61d64ac54802149d35ed6e1b728b815cb7a0d7f 0.000600000000 1748342 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": 1261185, "vin": [ { "gen": { "height": 1261175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91388c0bac6ceeadc2e14950f61d64ac54802149d35ed6e1b728b815cb7a0d7f" } } ], "extra": [ 1, 1, 97, 72, 234, 232, 219, 231, 234, 166, 141, 10, 165, 127, 237, 54, 82, 113, 38, 78, 98, 235, 122, 72, 151, 109, 252, 229, 212, 146, 45, 132, 173, 2, 17, 0, 0, 0, 2, 219, 181, 113, 193, 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: