Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 995e1f8f1ae3e2a42a67f66b8b59b435235320d138ef51765bf8b6e3b7270f92

Tx prefix hash: 5decf28dd33117124aa69482f3f7a0024473cf1d54847fc7236f59a6e3eb61ca
Tx public key: 1088479d026648f81a6d738296e55333d40ad56b01368171324b3d61effa9d8b
Timestamp: 1577813411 Timestamp [UTC]: 2019-12-31 17:30:11 Age [y:d:h:m:s]: 06:238:06:03:04
Block: 35914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1584367 RingCT/type: yes/0
Extra: 011088479d026648f81a6d738296e55333d40ad56b01368171324b3d61effa9d8b0211000000384943cd9f000000000000000000

1 output(s) for total of 0.466662456694 xmr

stealth address amount amount idx tag
00: ff5fe687a20fa88fb5241f28ac6fc8736724fa9c0ec1fea028eef46e81bed67c 0.466662456694 60654 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": 35924, "vin": [ { "gen": { "height": 35914 } } ], "vout": [ { "amount": 466662456694, "target": { "key": "ff5fe687a20fa88fb5241f28ac6fc8736724fa9c0ec1fea028eef46e81bed67c" } } ], "extra": [ 1, 16, 136, 71, 157, 2, 102, 72, 248, 26, 109, 115, 130, 150, 229, 83, 51, 212, 10, 213, 107, 1, 54, 129, 113, 50, 75, 61, 97, 239, 250, 157, 139, 2, 17, 0, 0, 0, 56, 73, 67, 205, 159, 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: