Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64bbc2303a8b59c9949161db8ca43ad325ff657c4a45632850cf6942f08bdbee

Tx prefix hash: b68ccc1c22cabd8f5c268918c0160ead017507b804f588d3c20fe849d40879ef
Tx public key: 417fd349dc53c0c5f6fe42c3925aed5e22c745e1a72d3566d8580f26f8154a32
Timestamp: 1731050539 Timestamp [UTC]: 2024-11-08 07:22:19 Age [y:d:h:m:s]: 02:011:02:01:04
Block: 1149086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 532702 RingCT/type: yes/0
Extra: 01417fd349dc53c0c5f6fe42c3925aed5e22c745e1a72d3566d8580f26f8154a320211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9ea4ffd497f69ed675b4e7376f5294257d728ecbf9d69e7ccc543ffe1514e30f 0.000600000000 1634087 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": 1149096, "vin": [ { "gen": { "height": 1149086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ea4ffd497f69ed675b4e7376f5294257d728ecbf9d69e7ccc543ffe1514e30f" } } ], "extra": [ 1, 65, 127, 211, 73, 220, 83, 192, 197, 246, 254, 66, 195, 146, 90, 237, 94, 34, 199, 69, 225, 167, 45, 53, 102, 216, 88, 15, 38, 248, 21, 74, 50, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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: