Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 640224d7fed4e2b8882336e646432407cd707d6f7067079208aef13cafc1fcc6

Tx prefix hash: 67863c1716350cda5570f672d1e75f1432e1ffd870f76a4d14f45c7499b7297d
Tx public key: 8e19ebfa42b3d6a91b1902ed251e9f1268fd3e15df414a1585de8da13107fed7
Timestamp: 1665114557 Timestamp [UTC]: 2022-10-07 03:49:17 Age [y:d:h:m:s]: 04:047:03:56:47
Block: 603665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1079829 RingCT/type: yes/0
Extra: 018e19ebfa42b3d6a91b1902ed251e9f1268fd3e15df414a1585de8da13107fed7021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.006134897572 xmr

stealth address amount amount idx tag
00: 3cac958fb2ae0628e62a6024c4fab0fb50c7c35f01e1bec6b08825e81579b6aa 0.006134897572 1039876 of 0 -

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": 603675, "vin": [ { "gen": { "height": 603665 } } ], "vout": [ { "amount": 6134897572, "target": { "key": "3cac958fb2ae0628e62a6024c4fab0fb50c7c35f01e1bec6b08825e81579b6aa" } } ], "extra": [ 1, 142, 25, 235, 250, 66, 179, 214, 169, 27, 25, 2, 237, 37, 30, 159, 18, 104, 253, 62, 21, 223, 65, 74, 21, 133, 222, 141, 161, 49, 7, 254, 215, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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: