Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d183414ae64e6142cb917b33b352dcebf4eb601b13f4749229f96db548ab8d0

Tx prefix hash: 07d0e50cfdad9c8da721d3f6b7155562a9fbb6684f6c4ee3633399af7543a205
Tx public key: 61a8cee9b60e4c25a8d0c7b8df3d8f9d4c6493c6fcc517be34b82b385500502e
Timestamp: 1731402160 Timestamp [UTC]: 2024-11-12 09:02:40 Age [y:d:h:m:s]: 02:009:06:55:38
Block: 1151989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531505 RingCT/type: yes/0
Extra: 0161a8cee9b60e4c25a8d0c7b8df3d8f9d4c6493c6fcc517be34b82b385500502e021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 64bd9836055cb612de3cad500461aa43a54f00a89a840f42120e8b4fcd578e43 0.000600000000 1637580 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": 1151999, "vin": [ { "gen": { "height": 1151989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64bd9836055cb612de3cad500461aa43a54f00a89a840f42120e8b4fcd578e43" } } ], "extra": [ 1, 97, 168, 206, 233, 182, 14, 76, 37, 168, 208, 199, 184, 223, 61, 143, 157, 76, 100, 147, 198, 252, 197, 23, 190, 52, 184, 43, 56, 85, 0, 80, 46, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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: