Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 030c8499ae13d7452a66a696b4e31730fb581f6a3afadcbdb71c312c2cb389fc

Tx prefix hash: ef47b73be8919eb4c00b9289b6af9e3d0ffd4eab1ee02450450804747c6cde2b
Tx public key: 255010c85eb3d69c8c8d518d094b6ae50ceb1224250bed5b5b4e23260b2ab62b
Timestamp: 1749797857 Timestamp [UTC]: 2025-06-13 06:57:37 Age [y:d:h:m:s]: 00:270:20:35:04
Block: 1303987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191248 RingCT/type: yes/0
Extra: 01255010c85eb3d69c8c8d518d094b6ae50ceb1224250bed5b5b4e23260b2ab62b02110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 90d9324f7e8fb641763ffa8b1d517fcb6ff04e7392f97deda4411799cd7d0a69 0.000600000000 1791572 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": 1303997, "vin": [ { "gen": { "height": 1303987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90d9324f7e8fb641763ffa8b1d517fcb6ff04e7392f97deda4411799cd7d0a69" } } ], "extra": [ 1, 37, 80, 16, 200, 94, 179, 214, 156, 140, 141, 81, 141, 9, 75, 106, 229, 12, 235, 18, 36, 37, 11, 237, 91, 91, 78, 35, 38, 11, 42, 182, 43, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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