Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6970ecd6f3cd3f94485ad3ef41f4c9a833fd305d4ca7e23d663663ff2c0286c

Tx prefix hash: d3a31c308ad5d55350587d2a261d746716e505b8e01983f14acd5d81ad217ffd
Tx public key: 64b53f1925a2b27a273e7146735b7131388185b7a18626c8cb5be7ba1852ede5
Timestamp: 1579352515 Timestamp [UTC]: 2020-01-18 13:01:55 Age [y:d:h:m:s]: 06:306:22:07:58
Block: 48333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1633507 RingCT/type: yes/0
Extra: 0164b53f1925a2b27a273e7146735b7131388185b7a18626c8cb5be7ba1852ede502110000000549b77a3d000000000000000000

1 output(s) for total of 0.424476393212 xmr

stealth address amount amount idx tag
00: 6a45da69c8710ce0d662ca84fbfe6ee494a6690876a6541a1b6794ee652065e2 0.424476393212 89500 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": 48343, "vin": [ { "gen": { "height": 48333 } } ], "vout": [ { "amount": 424476393212, "target": { "key": "6a45da69c8710ce0d662ca84fbfe6ee494a6690876a6541a1b6794ee652065e2" } } ], "extra": [ 1, 100, 181, 63, 25, 37, 162, 178, 122, 39, 62, 113, 70, 115, 91, 113, 49, 56, 129, 133, 183, 161, 134, 38, 200, 203, 91, 231, 186, 24, 82, 237, 229, 2, 17, 0, 0, 0, 5, 73, 183, 122, 61, 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: