Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a453e2b3112ff092ade1e50e0bf2a461de30fc27d58b77a8a95ea855c5e2897

Tx prefix hash: fba60a885e55e73853220358a4cbce18ec46e7913333b86750b0e5ae71336377
Tx public key: ce7121c37041ee252f834f9cfa4df9930db69fc022eac22c32c33cdc57db7c13
Timestamp: 1706979118 Timestamp [UTC]: 2024-02-03 16:51:58 Age [y:d:h:m:s]: 02:291:22:12:49
Block: 949590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 733897 RingCT/type: yes/0
Extra: 01ce7121c37041ee252f834f9cfa4df9930db69fc022eac22c32c33cdc57db7c1302110000000459dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5f723f8b2e4e5be7136a5775028016ccbc94c8816545ca6f60a76ddf72e3b21c 0.000600000000 1408120 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": 949600, "vin": [ { "gen": { "height": 949590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f723f8b2e4e5be7136a5775028016ccbc94c8816545ca6f60a76ddf72e3b21c" } } ], "extra": [ 1, 206, 113, 33, 195, 112, 65, 238, 37, 47, 131, 79, 156, 250, 77, 249, 147, 13, 182, 159, 192, 34, 234, 194, 44, 50, 195, 60, 220, 87, 219, 124, 19, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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: