Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6560aec7ad01d2fd3ca043b205650e1f357e7a57c57d023320338b16b683443d

Tx prefix hash: e55ceb081ad7b8bf5136c03f65710f1f9a6edecdd9e637add0635beb6d77031b
Tx public key: 07a22dc931370f3fe52221cbf95ac64a361521065410c350958f252cbdcb0aa0
Timestamp: 1746357045 Timestamp [UTC]: 2025-05-04 11:10:45 Age [y:d:h:m:s]: 00:288:02:59:13
Block: 1275541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203552 RingCT/type: yes/0
Extra: 0107a22dc931370f3fe52221cbf95ac64a361521065410c350958f252cbdcb0aa00211000000091f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ed1638d0dc342128c39e1d0064008b3cc8262a41f3cf6f1951f3013435e02130 0.000600000000 1762854 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": 1275551, "vin": [ { "gen": { "height": 1275541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed1638d0dc342128c39e1d0064008b3cc8262a41f3cf6f1951f3013435e02130" } } ], "extra": [ 1, 7, 162, 45, 201, 49, 55, 15, 63, 229, 34, 33, 203, 249, 90, 198, 74, 54, 21, 33, 6, 84, 16, 195, 80, 149, 143, 37, 44, 189, 203, 10, 160, 2, 17, 0, 0, 0, 9, 31, 144, 81, 122, 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) | dinastycoin version: tesla-369