Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49b64c2db371869b2d7e5f102c58d2a5fd68b43a7b51364523a64a3eefd3bbf6

Tx prefix hash: cb2d081c2a4ea1dd9a8426a451846de7ff60c239aab98976ba4a51e2bcf3c62f
Tx public key: 1b30902d154c03f8c7b6bc5e5f97a1abd138e12a00389cdd0a994b52a72b0092
Timestamp: 1704444913 Timestamp [UTC]: 2024-01-05 08:55:13 Age [y:d:h:m:s]: 02:059:14:36:45
Block: 928580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 562249 RingCT/type: yes/0
Extra: 011b30902d154c03f8c7b6bc5e5f97a1abd138e12a00389cdd0a994b52a72b00920211000000010011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5a4d1f2683640c3787fd4284630a92215325358f45082a32fb15c1706235b1cc 0.000600000000 1386440 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": 928590, "vin": [ { "gen": { "height": 928580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a4d1f2683640c3787fd4284630a92215325358f45082a32fb15c1706235b1cc" } } ], "extra": [ 1, 27, 48, 144, 45, 21, 76, 3, 248, 199, 182, 188, 94, 95, 151, 161, 171, 209, 56, 225, 42, 0, 56, 156, 221, 10, 153, 75, 82, 167, 43, 0, 146, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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