Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ccdeb9c3a9a86fec0a8a1786bda497a7dc71f4a32f8368d80d469767c6cbe01

Tx prefix hash: ceeefd5bf0a44fb43111b2e8c61cd01150dd3b02a362576d904cafe84930dc2d
Tx public key: 2f8b8bf8309da7d7812e7beab1cc8060409c55ef8eedbca7ab052293e5c29e36
Timestamp: 1771400829 Timestamp [UTC]: 2026-02-18 07:47:09 Age [y:d:h:m:s]: 00:272:14:57:57
Block: 1480328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200366 RingCT/type: yes/0
Extra: 012f8b8bf8309da7d7812e7beab1cc8060409c55ef8eedbca7ab052293e5c29e36021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 90d97665bd4098b4bf5340bd3c283113129553293332468f4bb957f3dd1d01ac 0.000600000000 1969696 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": 1480338, "vin": [ { "gen": { "height": 1480328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90d97665bd4098b4bf5340bd3c283113129553293332468f4bb957f3dd1d01ac" } } ], "extra": [ 1, 47, 139, 139, 248, 48, 157, 167, 215, 129, 46, 123, 234, 177, 204, 128, 96, 64, 156, 85, 239, 142, 237, 188, 167, 171, 5, 34, 147, 229, 194, 158, 54, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: