Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 196c3bbde1ad9b088b8833f8faaffb4e87f80bdb5c846ee93c05286d10d59140

Tx prefix hash: 52ba33606a6e577d44c31b0d2aa8e23a4be236c7a00eb2ad4a7a8f329c16286d
Tx public key: 186c96eaff6e15e92f1cb32dfbd69e46f633954ee06d894749df4828415694b9
Timestamp: 1775264274 Timestamp [UTC]: 2026-04-04 00:57:54 Age [y:d:h:m:s]: 00:191:06:54:34
Block: 1512311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140364 RingCT/type: yes/0
Extra: 01186c96eaff6e15e92f1cb32dfbd69e46f633954ee06d894749df4828415694b9021100000007ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4f4f095b4dc0bb4f968a2b63ba8d4ca964c67f8ef92d3ad5af6d1b304d698cfa 0.000600000000 2002111 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": 1512321, "vin": [ { "gen": { "height": 1512311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f4f095b4dc0bb4f968a2b63ba8d4ca964c67f8ef92d3ad5af6d1b304d698cfa" } } ], "extra": [ 1, 24, 108, 150, 234, 255, 110, 21, 233, 47, 28, 179, 45, 251, 214, 158, 70, 246, 51, 149, 78, 224, 109, 137, 71, 73, 223, 72, 40, 65, 86, 148, 185, 2, 17, 0, 0, 0, 7, 238, 75, 113, 129, 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: