Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c929d6e5b9977be364f35fbb47c38e678ab24df878ff1c19dd3de4b94b178db9

Tx prefix hash: 8e132a7e43ff56db7d7bcb2e8790cac45826577d737ebd101be04d2059f357f8
Tx public key: f458519fd2740151a9dcb0dab5bedd2983390dd967ec242387d285e3241af3c5
Timestamp: 1742534353 Timestamp [UTC]: 2025-03-21 05:19:13 Age [y:d:h:m:s]: 01:246:17:44:13
Block: 1243910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440240 RingCT/type: yes/0
Extra: 01f458519fd2740151a9dcb0dab5bedd2983390dd967ec242387d285e3241af3c5021100000005ed95dce7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cb07568417446199c1d034b84b971eec58fb5176e1d652b0912a0c7f8e4ec8a3 0.000600000000 1730901 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": 1243920, "vin": [ { "gen": { "height": 1243910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb07568417446199c1d034b84b971eec58fb5176e1d652b0912a0c7f8e4ec8a3" } } ], "extra": [ 1, 244, 88, 81, 159, 210, 116, 1, 81, 169, 220, 176, 218, 181, 190, 221, 41, 131, 57, 13, 217, 103, 236, 36, 35, 135, 210, 133, 227, 36, 26, 243, 197, 2, 17, 0, 0, 0, 5, 237, 149, 220, 231, 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: