Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36b964413c4a7bcbe88830ca6fe89a523bf621ab55cfd7c61ba211d204bf9dac

Tx prefix hash: 721b22cb422076a4adf43b4b52c0639ef487a71e2ad231f68d627f1309390a4f
Tx public key: ad22797cf7064f057ed513522c2210f924b8af37140216b4221959001da0d416
Timestamp: 1744107433 Timestamp [UTC]: 2025-04-08 10:17:13 Age [y:d:h:m:s]: 00:313:07:03:54
Block: 1256912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221560 RingCT/type: yes/0
Extra: 01ad22797cf7064f057ed513522c2210f924b8af37140216b4221959001da0d416021100000003dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b2d837020795c4e369a7ab7364d9ea74ec02e9cc7b1bfe7cd939e6c2a52d5b2c 0.000600000000 1744029 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": 1256922, "vin": [ { "gen": { "height": 1256912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2d837020795c4e369a7ab7364d9ea74ec02e9cc7b1bfe7cd939e6c2a52d5b2c" } } ], "extra": [ 1, 173, 34, 121, 124, 247, 6, 79, 5, 126, 213, 19, 82, 44, 34, 16, 249, 36, 184, 175, 55, 20, 2, 22, 180, 34, 25, 89, 0, 29, 160, 212, 22, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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