Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70f253dfceb1e4539f6ce8ceba1ed2c4979becc5ca51b10e859c8ca47ef1879f

Tx prefix hash: 46524bed2668518c9d889c9979bdcea415f7d661411797d86113ae8be7b4c678
Tx public key: 5d7fd7a86565097b9396801c130cd9c1264c6a58b076c0e2dcbdf3b9d9d0b303
Timestamp: 1644903473 Timestamp [UTC]: 2022-02-15 05:37:53 Age [y:d:h:m:s]: 04:277:23:33:30
Block: 438949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1242708 RingCT/type: yes/0
Extra: 015d7fd7a86565097b9396801c130cd9c1264c6a58b076c0e2dcbdf3b9d9d0b303021100000001d3fcec30000000000000000000

1 output(s) for total of 0.021556589003 xmr

stealth address amount amount idx tag
00: 736b6674541f7fbd85bd280bf6fa9ea455e332111677a709ccad91a811c279db 0.021556589003 850944 of 0 -

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": 438959, "vin": [ { "gen": { "height": 438949 } } ], "vout": [ { "amount": 21556589003, "target": { "key": "736b6674541f7fbd85bd280bf6fa9ea455e332111677a709ccad91a811c279db" } } ], "extra": [ 1, 93, 127, 215, 168, 101, 101, 9, 123, 147, 150, 128, 28, 19, 12, 217, 193, 38, 76, 106, 88, 176, 118, 192, 226, 220, 189, 243, 185, 217, 208, 179, 3, 2, 17, 0, 0, 0, 1, 211, 252, 236, 48, 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: