Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d73f5fd1aa4e9b31dd09f6dabd7f8ff052460d77f89ff16cea9f65ab29e40a13

Tx prefix hash: 2fa36838f41e1c025e6f5b207303dbff3cce3008782313997f3daa1e773effe5
Tx public key: 786cce7bee219e24833e770c9fae55403f28aaf8f955617dda1b27c247023d45
Timestamp: 1774545926 Timestamp [UTC]: 2026-03-26 17:25:26 Age [y:d:h:m:s]: 00:236:01:18:57
Block: 1506363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174204 RingCT/type: yes/0
Extra: 01786cce7bee219e24833e770c9fae55403f28aaf8f955617dda1b27c247023d45021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d955ad1d14f9fb8f0e3f6ce79ddf05069f7f895d640bdd1fac9daa30a7390ca8 0.000600000000 1996107 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": 1506373, "vin": [ { "gen": { "height": 1506363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d955ad1d14f9fb8f0e3f6ce79ddf05069f7f895d640bdd1fac9daa30a7390ca8" } } ], "extra": [ 1, 120, 108, 206, 123, 238, 33, 158, 36, 131, 62, 119, 12, 159, 174, 85, 64, 63, 40, 170, 248, 249, 85, 97, 125, 218, 27, 39, 194, 71, 2, 61, 69, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 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: