Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d2998f0ce03e3130ef0df3f06c5c68daf6400e07202877eafd7e87eb184a01e

Tx prefix hash: 3df533e2ce987359a98408726a5a3bff629718c1e5c20cc39248c9de19978e43
Tx public key: f182d2a4c89b6dbf342d0695b0b4354467c120671eb20d35abd0a100940ff7b8
Timestamp: 1721223621 Timestamp [UTC]: 2024-07-17 13:40:21 Age [y:d:h:m:s]: 01:303:11:37:18
Block: 1067712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467790 RingCT/type: yes/0
Extra: 01f182d2a4c89b6dbf342d0695b0b4354467c120671eb20d35abd0a100940ff7b802110000000d91e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e4b68fc2d69de5f87326c22774b1e42f3108bdc803452a2a36ac136022b89774 0.000600000000 1538601 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": 1067722, "vin": [ { "gen": { "height": 1067712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4b68fc2d69de5f87326c22774b1e42f3108bdc803452a2a36ac136022b89774" } } ], "extra": [ 1, 241, 130, 210, 164, 200, 155, 109, 191, 52, 45, 6, 149, 176, 180, 53, 68, 103, 193, 32, 103, 30, 178, 13, 53, 171, 208, 161, 0, 148, 15, 247, 184, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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: