Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 413e816c0eb80d37f2b5e37e28211b82e96c9a2abc919fba63a6fd960c98a8e2

Tx prefix hash: f4c98a22275fb2d222e044b1bd53af9491f803592bd93789a28506d5a6a6b14c
Tx public key: 5af7cc9a3387fabe6a14279fd34c3a9c68b7c2f53a48b786000e8beb43e25c09
Timestamp: 1721637522 Timestamp [UTC]: 2024-07-22 08:38:42 Age [y:d:h:m:s]: 02:116:03:29:51
Block: 1071123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 607755 RingCT/type: yes/0
Extra: 015af7cc9a3387fabe6a14279fd34c3a9c68b7c2f53a48b786000e8beb43e25c09021100000005e914dd15000000000000000000

1 output(s) for total of 0.000615600000 xmr

stealth address amount amount idx tag
00: 74689e965ee54803f4dbe5897a763156a22e3701d182aa193b815bed65a1d5cb 0.000615600000 1543230 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": 1071133, "vin": [ { "gen": { "height": 1071123 } } ], "vout": [ { "amount": 615600000, "target": { "key": "74689e965ee54803f4dbe5897a763156a22e3701d182aa193b815bed65a1d5cb" } } ], "extra": [ 1, 90, 247, 204, 154, 51, 135, 250, 190, 106, 20, 39, 159, 211, 76, 58, 156, 104, 183, 194, 245, 58, 72, 183, 134, 0, 14, 139, 235, 67, 226, 92, 9, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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: