Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13f6385b2acaa72259b3b0706dd86d01c3d7a265fc7cb2356d7272f0ea364d19

Tx prefix hash: d361624d622e89ea410e009210dc77e0e81b7884d4d13b9c0af6577621353e2e
Tx public key: fa36ffc0cc339a103148d97cba6816c2acbc905680225e1ccd59162632c71c05
Timestamp: 1742161600 Timestamp [UTC]: 2025-03-16 21:46:40 Age [y:d:h:m:s]: 01:248:12:41:23
Block: 1240830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441789 RingCT/type: yes/0
Extra: 01fa36ffc0cc339a103148d97cba6816c2acbc905680225e1ccd59162632c71c05021100000005007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fbc1d4df4c5e7f774f3a0fabc85c3b16f0379840e54c07e58160ba7e23d6abca 0.000600000000 1727803 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": 1240840, "vin": [ { "gen": { "height": 1240830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbc1d4df4c5e7f774f3a0fabc85c3b16f0379840e54c07e58160ba7e23d6abca" } } ], "extra": [ 1, 250, 54, 255, 192, 204, 51, 154, 16, 49, 72, 217, 124, 186, 104, 22, 194, 172, 188, 144, 86, 128, 34, 94, 28, 205, 89, 22, 38, 50, 199, 28, 5, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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: